This unit describes the skills and knowledge required to design, build, and test a user interface (UI) to specification, including command-line interfaces (CLI), graphical user interfaces (GUI), web user interfaces (WUI) and natural user interfaces (NUI).

It applies to individuals who work as user-interface designers, and are responsible for specifying the layout and style of the desired user interface. They may be developers working in the area of user interface design and implementation.

No licensing, legislative or certification requirements apply to this unit at the time of publication.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT	PERFORMANCE CRITERIA
Elements describe the essential outcomes.	Performance criteria describe the performance needed to demonstrate achievement of the element.
1. Build a prototype user interface (UI)	1.1 Gather the requirements for the UI 1.2 Determine the application development language for writing the UI 1.3 Build a prototype, using the prototyping tools available in the determined language 1.4 Review the UI prototype with the client, and edit as required
2. Design the UI	2.1 Formulate the application content flow 2.2 Design the UI components 2.3 Define UI actions 2.4 Itemise UI events
3. Build the UI	3.1 Determine the appropriate language 3.2 Build the UI with the required functionality
4. Test the UI	4.1 Test the UI for overall functionality, according to requirements 4.2 Iterate the UI design, or build, until the test results meet requirements
5. Document the UI and obtain client sign-off	5.1 Document the user requirements 5.2 Document the UI 5.3 Obtain client sign-off to the completed UI

Evidence of the ability to:

design a fully functional user interface (UI) in consultation with the user, using the determined language

create a prototype UI

review the prototype with the user

build the UI

test that the UI is complete, consistent and functional

document the user requirements, UI and client sign-off.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

apply a range of basic mathematical strategies

use object-oriented programming

use open-source development tools

describe the process of small-size application development.

conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

the internet, to use the online tools available for prototyping and UI design

an integrated development environment (IDE) for the determined language

specific tools and licenses available, depending on the particular platform including:

Windows

Linux

Unix

Mac

Google Chrome.

Assessors must satisfy NVR/AQTF assessor requirements.

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT	PERFORMANCE CRITERIA
Elements describe the essential outcomes.	Performance criteria describe the performance needed to demonstrate achievement of the element.
1. Build a prototype user interface (UI)	1.1 Gather the requirements for the UI 1.2 Determine the application development language for writing the UI 1.3 Build a prototype, using the prototyping tools available in the determined language 1.4 Review the UI prototype with the client, and edit as required
2. Design the UI	2.1 Formulate the application content flow 2.2 Design the UI components 2.3 Define UI actions 2.4 Itemise UI events
3. Build the UI	3.1 Determine the appropriate language 3.2 Build the UI with the required functionality
4. Test the UI	4.1 Test the UI for overall functionality, according to requirements 4.2 Iterate the UI design, or build, until the test results meet requirements
5. Document the UI and obtain client sign-off	5.1 Document the user requirements 5.2 Document the UI 5.3 Obtain client sign-off to the completed UI

Evidence of the ability to:

design a fully functional user interface (UI) in consultation with the user, using the determined language

create a prototype UI

review the prototype with the user

build the UI

test that the UI is complete, consistent and functional

document the user requirements, UI and client sign-off.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

apply a range of basic mathematical strategies

use object-oriented programming

use open-source development tools

describe the process of small-size application development.

conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

the internet, to use the online tools available for prototyping and UI design

an integrated development environment (IDE) for the determined language

specific tools and licenses available, depending on the particular platform including:

Windows

Linux

Unix

Mac

Google Chrome.

Assessors must satisfy NVR/AQTF assessor requirements.

Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice	Yes	No	Comments/feedback
Gather the requirements for the UI
Determine the application development language for writing the UI
Build a prototype, using the prototyping tools available in the determined language
Review the UI prototype with the client, and edit as required
Formulate the application content flow
Design the UI components
Define UI actions
Itemise UI events
Determine the appropriate language
Build the UI with the required functionality
Test the UI for overall functionality, according to requirements
Iterate the UI design, or build, until the test results meet requirements
Document the user requirements
Document the UI
Obtain client sign-off to the completed UI

Assessment Cover Sheet

ICTPRG410 - Build a user interface

Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICTPRG410 - Build a user interface

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: